Skip to main content

C# : Implementing Redis Pub/Sub Message Broker - Order processing example

 



In distributed systems, communication between components is essential for real-time data processing and coordination. Redis Pub/Sub (Publisher/Subscriber) provides a lightweight and efficient mechanism for message broadcasting and consumption. In this blog post, we'll explore how to implement Redis Pub/Sub as a message broker in C# applications, enabling seamless communication between different parts of the system.

1. Setting Up Redis Server: Before implementing Redis Pub/Sub in C#, ensure you have a Redis server up and running. You can install Redis locally or use a cloud-based Redis service provider like Azure Redis Cache or AWS ElastiCache.

2. Installing Redis Client Library: To interact with Redis from a C# application, you'll need to install a Redis client library. One popular choice is StackExchange.Redis, a high-performance Redis client library for .NET.

dotnet add package StackExchange.Redis
3. Publisher Implementation: The publisher component in your application is responsible for publishing messages to specific channels in Redis.
using StackExchange.Redis;

public class RedisPublisher
{
    private readonly ConnectionMultiplexer _redis;
    private readonly ISubscriber _subscriber;

    public RedisPublisher(string connectionString)
    {
        _redis = ConnectionMultiplexer.Connect(connectionString);
        _subscriber = _redis.GetSubscriber();
    }

    public void PublishMessage(string channel, string message)
    {
        _subscriber.Publish(channel, message);
    }
}
4. Subscriber Implementation: The subscriber component listens for messages on specific channels and performs actions accordingly.
using StackExchange.Redis;

public class RedisSubscriber
{
    private readonly ConnectionMultiplexer _redis;
    private readonly ISubscriber _subscriber;

    public RedisSubscriber(string connectionString)
    {
        _redis = ConnectionMultiplexer.Connect(connectionString);
        _subscriber = _redis.GetSubscriber();
    }

    public void SubscribeToChannel(string channel, Action<RedisChannel, RedisValue> handler)
    {
        _subscriber.Subscribe(channel, handler);
    }
}
5. Usage Example: Let's see how we can use the Redis Pub/Sub components in a C# application.
// Publisher
var publisher = new RedisPublisher("localhost");
publisher.PublishMessage("channelName", "Hello from Publisher!");

// Subscriber
var subscriber = new RedisSubscriber("localhost");
subscriber.SubscribeToChannel("channelName", (channel, message) =>
{
    Console.WriteLine($"Received message on channel {channel}: {message}");
});
Let's, implement an order processing system using Redis Pub/Sub as a message broker in a C# application. Redis Pub/Sub will facilitate communication between the order submission component and the order processing component, ensuring seamless processing of orders in real-time.

Order Submission Component: This component is responsible for submitting new orders to the system. We'll publish orders to a Redis channel named "new_orders".
using StackExchange.Redis;

public class OrderSubmitter
{
    private readonly ConnectionMultiplexer _redis;
    private readonly ISubscriber _subscriber;

    public OrderSubmitter(string connectionString)
    {
        _redis = ConnectionMultiplexer.Connect(connectionString);
        _subscriber = _redis.GetSubscriber();
    }

    public void SubmitOrder(Order order)
    {
        var message = JsonConvert.SerializeObject(order);
        _subscriber.Publish("new_orders", message);
    }
}
Order Processing Component: This component listens for new orders on the "new_orders" channel and processes them accordingly.
using StackExchange.Redis;

public class OrderProcessor
{
    private readonly ConnectionMultiplexer _redis;
    private readonly ISubscriber _subscriber;

    public OrderProcessor(string connectionString)
    {
        _redis = ConnectionMultiplexer.Connect(connectionString);
        _subscriber = _redis.GetSubscriber();
    }

    public void StartProcessingOrders()
    {
        _subscriber.Subscribe("new_orders", (channel, message) =>
        {
            var order = JsonConvert.DeserializeObject<Order>(message);
            ProcessOrder(order);
        });
    }

    private void ProcessOrder(Order order)
    {
        // Process the order (e.g., validate, update inventory, send confirmation)
        Console.WriteLine($"Processing order: {order.OrderId}");
    }
}
Usage Example: Let's see how to use the order submission and processing components in a C# application.
// Order submission
var submitter = new OrderSubmitter("localhost");
var order = new Order { OrderId = 123, CustomerId = 456, TotalAmount = 100 };
submitter.SubmitOrder(order);

// Order processing
var processor = new OrderProcessor("localhost");
processor.StartProcessingOrders();
Conclusion: By leveraging Redis Pub/Sub in a C# application, we've implemented an efficient order processing system where new orders are submitted and processed in real-time. The publisher-subscriber model provided by Redis Pub/Sub ensures seamless communication between different parts of the system, enabling scalable and responsive order processing workflows. Whether it's handling incoming orders, updating inventory, or sending order confirmations, Redis Pub/Sub serves as a powerful tool for building event-driven architectures in C# applications.

Comments

Popular posts from this blog

Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

.NET 10: Your Ultimate Guide to the Coolest New Features (with Real-World Goodies!)

 Hey .NET warriors! 🤓 Are you ready to explore the latest and greatest features that .NET 10 and C# 14 bring to the table? Whether you're a seasoned developer or just starting out, this guide will show you how .NET 10 makes your apps faster, safer, and more productive — with real-world examples to boot! So grab your coffee ☕️ and let’s dive into the awesome . 💪 1️⃣ JIT Compiler Superpowers — Lightning-Fast Apps .NET 10 is all about speed . The Just-In-Time (JIT) compiler has been turbocharged with: Stack Allocation for Small Arrays 🗂️ Think fewer heap allocations, less garbage collection, and blazing-fast performance . Better Code Layout 🔥 Hot code paths are now smarter, meaning faster method calls and fewer CPU cache misses. 💡 Why you care: Your APIs, desktop apps, and services now respond quicker — giving users a snappy experience . 2️⃣ Say Hello to C# 14 — More Power in Your Syntax .NET 10 ships with C# 14 , and it’s packed with developer goodies: Field-Bac...

Optional Parameters in C# — Writing Flexible and Clean Methods

Hello, .NET developers! 👋 How often have you created multiple method overloads just to handle slightly different cases? Maybe one method accepts two parameters, another three, and one more adds a flag for debugging? That’s a lot of code duplication for something that can be solved beautifully with optional parameters . Optional parameters in C# let you define default values for method arguments. When a caller doesn’t pass a value, the compiler automatically substitutes the default. This feature helps keep your APIs simple, readable, and maintainable. 🎥 Explore more on YouTube : DotNet Full Stack Dev Understanding Optional Parameters Optional parameters are defined by assigning default values in the method signature. When calling the method, you can omit those parameters if you’re okay with the defaults. Example public class Logger { public void Log(string message, string level = "INFO", bool writeToFile = false) ...